Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0352

reference: 165-tree-1
name: 0352
tree-preservation-order: undefined
165-tpo-1
uprn
address-text
point: POINT (-0.999789 50.857023)
geometry: MULTIPOLYGON (((-0.999690 50.857012,-0.999694 50.857031,-0.999708 50.857049,-0.999730 50.857063,-0.999757 50.857072,-0.999788 50.857076,-0.999819 50.857073,-0.999846 50.857064,-0.999869 50.857050,-0.999883 50.857033,-0.999889 50.857014,-0.999884 50.856994,-0.999870 50.856977,-0.999849 50.856962,-0.999821 50.856953,-0.999790 50.856950,-0.999760 50.856953,-0.999732 50.856961,-0.999709 50.856975,-0.999695 50.856993,-0.999690 50.857012)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL